Correct CO2 Management Data#273
Open
toniseibold wants to merge 5 commits into
Open
Conversation
6 tasks
There was a problem hiding this comment.
Pull request overview
This PR updates the cost/energy assumptions for the CO2 liquefaction technology (used for CO2 conditioning/compression for transport) by replacing the previous Mitsubishi/IEA (2004, ship transport) reference with values from the 2024 AIT study, and propagates the update into generated output cost tables (global and US) plus release notes.
Changes:
- Replace
CO2 liquefactionCAPEX/FOM/electricity-input source data with AIT study values (and remove the previous heat-input row). - Update
inputs/manual_input.csvso the compilation pipeline produces the newCO2 liquefactionoutputs. - Add an “Upcoming Release” note documenting the CO2 dense-phase compression update.
Reviewed changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| outputs/US/costs_2050.csv | Updates US output rows for CO2 liquefaction to AIT-based assumptions. |
| outputs/US/costs_2045.csv | Same AIT-based CO2 liquefaction update for 2045 US outputs. |
| outputs/US/costs_2040.csv | Same AIT-based CO2 liquefaction update for 2040 US outputs. |
| outputs/US/costs_2035.csv | Same AIT-based CO2 liquefaction update for 2035 US outputs. |
| outputs/US/costs_2030.csv | Same AIT-based CO2 liquefaction update for 2030 US outputs. |
| outputs/US/costs_2025.csv | Same AIT-based CO2 liquefaction update for 2025 US outputs. |
| outputs/US/costs_2020.csv | Same AIT-based CO2 liquefaction update for 2020 US outputs. |
| outputs/costs_2050.csv | Updates global output rows for CO2 liquefaction to AIT-based assumptions. |
| outputs/costs_2045.csv | Same AIT-based CO2 liquefaction update for 2045 global outputs. |
| outputs/costs_2040.csv | Same AIT-based CO2 liquefaction update for 2040 global outputs. |
| outputs/costs_2035.csv | Same AIT-based CO2 liquefaction update for 2035 global outputs. |
| outputs/costs_2030.csv | Same AIT-based CO2 liquefaction update for 2030 global outputs. |
| outputs/costs_2025.csv | Same AIT-based CO2 liquefaction update for 2025 global outputs. |
| outputs/costs_2020.csv | Same AIT-based CO2 liquefaction update for 2020 global outputs. |
| inputs/manual_input.csv | Replaces the underlying manual input entries for CO2 liquefaction with AIT-based data. |
| docs/release_notes.rst | Adds an Upcoming Release bullet about the CO2 dense-phase compression update. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
bobbyxng
reviewed
May 11, 2026
bobbyxng
reviewed
May 11, 2026
bobbyxng
left a comment
bobbyxng
left a comment
There was a problem hiding this comment.
Generally looks good to me, two comments
- consider moving
CO2 liquefaction,carbondioxide-input,0,1,t_CO2/t_CO2,-,,into config.default of the pypsa-eur workflow, as this does not add any new data to technology.data - Add to release_notes the rather big change in CO2 liquefaction capital cost (which make sense as the previous value was simply wrong)
fneum
requested changes
May 12, 2026
Member
fneum
left a comment
fneum
left a comment
There was a problem hiding this comment.
Looks good, but what I don't understand is the origin of the big cost difference. Perhaps you can explain?
Is the application / process really different? And if yes, should this perhaps be two separate technology names? Could double-check how TRACE uses "CO2 liquefaction" and if current use would be correct there.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correcting:
Checklist
doc. not applicableenvironment.yaml(if applicable). not applicabledoc/release_notes.rstof the upcoming release is included.